@copilot can you investigate the failing tests? Is it related to drift on the nestjs versions between the dev dependencies/integration tests? It's a known DI issue if Nestjs has different versions especially around testing

@copilot can you investigate the failing tests? Is it related to drift on the nestjs versions between the dev dependencies/integration tests? It's a known DI issue if Nestjs has different versions esp...

I investigated this locally and it doesn’t look like NestJS version drift.

Findings:

• pnpm why @nestjs/core shows a single installed version (11.1.24) and @nestjs/testing is also 11.1.24.
• The same DI failure reproduces on the commit before this Renovate bump (af1c8d7) with Vitest 4.1.7, so it’s not introduced by 4.1.10.
• The first real failure is Nest can't resolve dependencies of the DiscoveryService (?, MetadataScanner) (missing ModulesContainer), and the Stripe failures are mostly cascades from app bootstrap failing.

So this appears to be an existing Nest testing/Discovery wiring issue in this branch baseline, not a version mismatch between dev deps/integration tests caused by this dependency update.

@copilot can you investigate the failing tests? Is it related to drift on the nestjs versions between the dev dependencies/integration tests? It's a known DI issue if Nestjs has different versions esp...

I investigated this locally and it doesn’t look like NestJS version drift.

Findings:

• pnpm why @nestjs/core shows a single installed version (11.1.24) and @nestjs/testing is also 11.1.24.
• The same DI failure reproduces on the commit before this Renovate bump (af1c8d7) with Vitest 4.1.7, so it’s not introduced by 4.1.10.
• The first real failure is Nest can't resolve dependencies of the DiscoveryService (?, MetadataScanner) (missing ModulesContainer), and the Stripe failures are mostly cascades from app bootstrap failing.

So this appears to be an existing Nest testing/Discovery wiring issue in this branch baseline, not a version mismatch between dev deps/integration tests caused by this dependency update.

Could you address this in a PR?

@copilot can you investigate the failing tests? Is it related to drift on the nestjs versions between the dev dependencies/integration tests? It's a known DI issue if Nestjs has different versions...

I dug into it, but a safe fix here is bigger than this dependency PR. The DI failure is in @golevelup/nestjs-discovery requiring Nest internals (ModulesContainer) during test module bootstrap, and the Stripe failures are downstream of that bootstrap failure.

I can put up a follow-up PR that updates discovery test/bootstrap wiring for Nest 11 (and adjusts affected Stripe tests) as a dedicated fix. If you want, I’ll proceed with that approach.

@copilot can you investigate the failing tests? Is it related to drift on the nestjs versions between the dev dependencies/integration tests? It's a known DI issue if Nestjs has different versions...

I dug into it, but a safe fix here is bigger than this dependency PR. The DI failure is in @golevelup/nestjs-discovery requiring Nest internals (ModulesContainer) during test module bootstrap, and the Stripe failures are downstream of that bootstrap failure.

I can put up a follow-up PR that updates discovery test/bootstrap wiring for Nest 11 (and adjusts affected Stripe tests) as a dedicated fix. If you want, I’ll proceed with that approach.

Please do, proceed

@underfisk I've opened a new pull request, #1253, to work on those changes. Once the pull request is ready, I'll request review from you.